Extended Metrics to Evaluate Cost Effectiveness of Software Inspections
نویسندگان
چکیده
For more than twenty-five years software inspections have been considered an effective and efficient method for software quality improvement [3,4,9]. The goal of inspections is to detect defect before the testing stage begins. According to the data published in the literature, software design inspections save on average 44% of the defect detection costs, and code inspections save on average 39% of the defect detection costs [1]. However, are the software inspections always worthwhile? In order to evaluate the effectiveness of the inspections with respect to software development cost, several metrics have been previously proposed [2,3,6]. Collofello et al. have taken into account of the costs consumed and saved by inspections and proposed a metric, called Cost Effectiveness [2]. Kusumoto et al. proposed a metric Mk for evaluating cost effectiveness of inspections, which is based on the degree to which costs to detect all faults from the software in a project are reduced by inspections [6]. Yet, none of those metrics includes the information about false positives (the issues that require no repair) introduced during inspection, although the rework of false positives is costly and can introduce new defects [8,12]. This letter presents a) an inspection cost model that describes all costs related to inspections, b) extension of the metric Mk to evaluate the cost effectiveness as well as the losses of inspections. Proposed cost model and metrics can be useful for project managers to decide whether inspections are worthwhile. The structure of the letter is as follows. Section 2 describes the inspection process. Section 3 describes the inspection cost model. In Section 4, we review the existing metrics to evaluate software inspections. Section 5 presents the extended metrics for software inspection evaluation. In Section 6, we compare extended metrics to Collofello’s metric and Mk. Section 7 concludes the letter with an overall summary and directions for future research.
منابع مشابه
"What Makes Inspections Work?" Understanding How and Why Different Inspection Methods Impact Effectiveness and Cost
For two decades, software inspections have proven effective for detecting defects in software. We have reviewed the different ways sofhyare inspections are done, created a taxonomy of inspection methods, and examined claims about the cost-effectiveness of different methods. We detect a disturbingpattem in the evaluation of inspection methods. Although there is near universal agreement on the ef...
متن کاملIncreasing the Understanding of Effectiveness in Software Inspections Using Published Data Sets
Since its inception into software engineering, software inspection has been viewed as a costeffective way of increasing software quality. Despite this, many questions remain unanswered regarding, for example, ideal team size or cost effectiveness. This paper addresses some of these questions by performing an analysis using 30 published data sets from empirical experiments of software inspection...
متن کاملInvestigating Defect Detection in Object-Oriented Design and Cost-Effectiveness of Software Inspection
As the use of software grows in today’s society, software quality is becoming an increasingly important issue, and the need for activities to control and improve it is increasing dramatically. Software inspection has been extensively used for over thirty years to ensure the quality of software, by finding and repairing defects in software products. However, the yet narrow scope of research has ...
متن کاملSoftware Inspection Benchmarking - A Qualitative and Quantitative Comparative Opportunity
Software inspections are commonly used throughout the software industry, but there are still open questions about the relationship between inspection processes and inspection effectiveness. For example, which techniques work best in various environments? Are requirements specifications inspections and code inspections different in terms of effectiveness? What is the effectiveness in inspections...
متن کاملIn-Process Evaluation for Software Inspection and Test
The goal of software inspection and test is to reduce the expected cost of software failure over the life of a product. This paper extends the use of defect higgers, the eventsthat cause defects to be discovered, to help evaluate the effectiveness of inspections and test scenarios. In the case of inspections, the defect trigger is defined as a set of values that associate the shills of the insp...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
- IEICE Transactions
دوره 87-D شماره
صفحات -
تاریخ انتشار 2004